Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

CP: Move linux_license to engine v2. (#41863)#42006

Merged
CaseyHillers merged 1 commit into
flutter-team-archive:flutter-3.11-candidate.0from
godofredoc:cp_2_3
May 15, 2023
Merged

CP: Move linux_license to engine v2. (#41863)#42006
CaseyHillers merged 1 commit into
flutter-team-archive:flutter-3.11-candidate.0from
godofredoc:cp_2_3

Conversation

@godofredoc

Copy link
Copy Markdown
Contributor

CP: 9ee91b8

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the Flutter Style Guide and the C++, Objective-C, Java style guides.
  • I listed at least one issue that this PR fixes in the description above.
  • I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt. See testing the engine for instructions on writing and running engine tests.
  • I updated/added relevant documentation (doc comments with ///).
  • I signed the CLA.
  • All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Linux license v2 builds has been running successfully for a few days and it is ready to get moved to prod.

[C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style

@XilaiZhang XilaiZhang left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

images (1)

@CaseyHillers
CaseyHillers merged commit 9270e39 into flutter-team-archive:flutter-3.11-candidate.0 May 15, 2023
@godofredoc
godofredoc deleted the cp_2_3 branch June 2, 2023 18:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants